Hey @demensky, we've already had similar PRs in past and unfortunately, they didn't work for us.

Please take a look at this PR #6943 where you can find why it didn't work for us.

Did you maybe try to run the docs app and check whether the issue explained in the mentioned PR applies to the changes form this PR?

Hehe, have I now completely missed the point?

It looks like export type creates an issue for us, but this PR is doing the import type 😄

However, I'd still like to know whether the docs app has issues with these changes.

@jakovljevic-mladen, I checked the docs app and didn't find any problems with it.

Thanks to you, I also decided to add export type, checked it again and still found no problems. Apparently the problem is no longer relevant.

P.S. I deleted apps/rxjs.dev/src/generated before starting the docs app build.

Actually, I don't think we had an issue with ShareConfig page being rendered, but with links that point to the ShareConfig page or any other exported type page that we have.

So, to test it, please open config page locally and verify that link from this line works and that it points to GlobalConfig page.

@jakovljevic-mladen. Here's video proof. Although I would be very grateful if you also checked locally.

Cool, I think that should be good enough. I also checked pipelines and it seems that we don't have issues there as well, so I think it's fine.

In general, I think this is fine. It doesn't really "fix" my ask, which is I legit wish that VS Code would highlight types differently... but besides that, I think it's a solid add. It makes the code easier to grep, if maybe mildly annoying to refactor.

We might want to make the eslint rule an error if we want to keep it clean.